fix(bitbucket): PR sync stops resending diffstat, conflicts, statuses and permission every sweep - #27596

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

Bitbucket pull-request summaries now reuse diff-stat and mergeability results when both commit SHAs are available. The parsed pull-request model now includes the trimmed destination commit SHA as baseSha.

Changes: Bitbucket summary cache

Layer / File(s)

Summary

Commit-keyed summary cache and invalidation packages/source-control-bitbucket/src/server/bitbucketPullRequestJson.ts, packages/source-control-bitbucket/src/server/BitbucketPullRequestProvider.ts, packages/source-control-bitbucket/src/server/BitbucketPullRequestProvider.test.ts

The pull-request data includes a trimmed destination commit SHA as baseSha. The provider caches diff statistics and mergeability by repository, pull-request number, and both commit SHAs. The cache has a 256-entry limit and a 15-minute TTL for successful reads with mergeability data. The provider reads values directly when either SHA is unavailable. Cache invalidation can clear all entries or match a repository and optional pull-request number. Tests cover reuse, changed commits, invalidation, expiration, and mergeability read failures.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Bug fix · Severity of issue fixed: High

Sequence Diagram(s)

sequenceDiagram
  participant Provider as BitbucketPullRequestProvider
  participant API as Bitbucket API
  participant Cache as Summary cache
  Provider->>API: Fetch pull request and commit SHAs
  Provider->>Cache: Look up by repository, pull request, and SHAs
  alt Cache hit
    Cache-->>Provider: Return diff statistics and mergeability
  else Cache miss
    Provider->>API: Read diff statistics and mergeability
    API-->>Provider: Return summary data
    Provider->>Cache: Store result with expiration
  end

Loading

Possibly related PRs

• pingdotgg/t3code#27100: Reuses pull-request summary reads for unchanged commits in the separate GitCafe provider.

Suggested reviewers: maria-rcks, ahilles107

Merge Risk: Minimal · previous review fd237

The summary path appears to reduce repeat Bitbucket reads without breaking the sync snapshot. No identified issue needs resolution before normal merge checks.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title clearly and concisely describes the main Bitbucket sync change: preventing repeated diffstat, conflict, status, and permission requests.
Description check		The description includes complete Problem, Change, Scope and approval, and Verification sections. It explains the rate-limit issue, implementation, linked issue, tests, runtime results, and limitation…
Linked Issues check		[#27578] The Bitbucket summary path now performs one pull-request read per sync and does not request statuses or repository permission. It caches diffstat and conflicts by repository, pull-request num…
Out of Scope Changes check		The changes stay within [#27578]. The provider adds the summary read, bounded commit-stat caching, and invalidation needed for sync. The JSON model adds the destination commit hash needed for the cach…

Full details: Description check

Explanation

The description includes complete Problem, Change, Scope and approval, and Verification sections. It explains the rate-limit issue, implementation, linked issue, tests, runtime results, and limitations.

Full details: Linked Issues check

Explanation

[#27578] The Bitbucket summary path now performs one pull-request read per sync and does not request statuses or repository permission. It caches diffstat and conflicts by repository, pull-request number, source commit, and destination commit. It rereads those values after a commit change, cache expiry, explicit invalidation, or an unrecovered conflicts read. The added tests cover unchanged reads, commit changes, expiry, invalidation, and failed conflicts reads. The reported package tests and changed-file checks pass. The implementation uses one pull-request read per linked pull request instead of the issue's optional list-endpoint batching, but it meets the request-reduction objective.

Full details: Out of Scope Changes check

Explanation

The changes stay within [#27578]. The provider adds the summary read, bounded commit-stat caching, and invalidation needed for sync. The JSON model adds the destination commit hash needed for the cache key. The tests verify the new sync behavior. No unrelated product behavior appears in the reviewed diff.

Generate docstrings

• Commit to this branch
• Create a new PR

Generate unit tests (beta)

• Commit to this branch
• Create a new PR